Subject: HALT reason codes

From: "Steve Klein" <[email-masked]>
Date: Wed, 19 Apr 95 12:34:10 EDT

Well, I've sifted through the ton of mail on this subject and propose
the following for a reason code field for the HALT_DL and HALT_DL_NOACK
SSP messages:

 - six bytes of (optional) data on a HALT_DL or HALT_DL_NOACK message
   comprised of:

   - a two byte generic reason code

     I like Peter Gayek's suggestion of using the same circuit
     disconnect reason codes that appear in the DLSw MIB:

   - a four byte expanded reason code

     This would be vendor unique and correspond to something internal
     to a particular implementation.  It could be set to all zeroes if
     an expanded reason is not desired or known.

Generic reason codes

Here are the DLSw MIB circuit disconnect reason codes from Peter's note:

>(3) Enumerated reason code for circuit disconnect
>
>      1 - Received HALT_DL from partner
>      2 - Received HALT_DL_NOACK from partner
>      3 - Received DISC from end-station
>      4 - Detected DLC error with end-station
>      5 - Circuit-level protocol error (e.g., pacing)
>      6 - Transport connection closed normally
>      7 - Transport connection closed due to error
>      8 - Operator-initiated (mgt station or local console)
>
>    (discussion question:  should we distinguish for 6-7 why the
>     TC was closed and what the errors may have been?)

It appears that the circuit disconnect reason codes that would apply as
HALT reason codes are:

       3 - Received DISC from end-station
       4 - Detected DLC error with end-station
       5 - Circuit-level protocol error (e.g., pacing)
       8 - Operator-initiated (mgt station or local console)

What do ya'll think about this?

Steve